Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@test/ui-e2e/README.md`:
- Line 71: The unescaped pipe character in the inline flag `--env=<ci|pipeline>`
on line 71 of the table is being interpreted as a Markdown table column
separator, causing the table structure to break (MD056 error). Escape the pipe
character by adding a backslash before it in the flag value so that Markdown
treats it as literal text rather than a column delimiter, maintaining the
intended 2-column table layout.

In `@test/ui-e2e/run-ui-tests.sh`:
- Around line 70-82: In the CI/pipeline automation block where ENV is "ci" or
"pipeline", the npx playwright test command on line 81 passes TEST_ARGS verbatim
without enforcing headless mode. If TEST_ARGS contains a --headed flag, it will
override the intended automation behavior and can fail in headless-only
environments. Either filter out any --headed flags from TEST_ARGS before passing
them to the playwright test command, or explicitly add a --headed=false flag to
the npx playwright test invocation within the CI/pipeline conditional block to
ensure headless execution is enforced regardless of user-provided arguments.
- Around line 15-24: The .env file is being sourced before the script changes to
its own directory, causing the check for .env and the source command to look in
the caller's current working directory instead of the test/ui-e2e directory.
Move the cd "$(dirname "$0")" || exit 1 command to execute before the if [ -f
.env ] block so that the .env file is correctly loaded from the script's own
directory, not from wherever the script was invoked.

In `@test/ui-e2e/src/pages/ApplicationDetailsPage.ts`:
- Line 26: The assertion on the "Healthy" text is currently scoped to the entire
page via this.page.getByText, which can match unrelated UI elements and cause
false positives. Instead of using this.page.getByText('Healthy', { exact: true
}).first(), first locate the resource tree container element, then apply the
getByText selector to that specific container element rather than the whole page
to ensure you're only checking the health status within the correct UI region.

In `@test/ui-e2e/src/pages/ApplicationsPage.ts`:
- Around line 107-119: Scope the selectors in the sync panel operations to
prevent matching unintended elements. Instead of using page-wide selectors
(`this.page.getByRole()` and `this.page.getByText()`), scope the allLink
selector at line 107, the expectedResource text selector at line 115, and the
synchronize button selector at line 118 to the sync panel context that was
opened earlier with `appContainer.getByText('Sync')`. Store the sync panel
locator and use it to scope all three subsequent selectors to that specific
panel rather than querying the entire page.
- Around line 140-143: The appLink selector in the openApplication method uses
non-exact matching on both the filter and getByRole calls, which can incorrectly
match similarly-named applications (e.g., petclinic vs petclinic-dev). Add
exact: true to both the hasText filter and the getByRole link selector to ensure
precise matching. This pattern is already demonstrated elsewhere in the file at
line 13 for the Create button selector.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@test/ui-e2e/.auth/setup.ts`:
- Around line 62-72: The Welcome Tour handling in setup should only ignore the
expected “not visible within timeout” case, not every exception. Update the
try/catch around the skipTourButton wait/click logic so that errors from
page.getByRole, skipTourButton.waitFor, and skipTourButton.click are checked for
timeout/not-present behavior and only those are logged and ignored; rethrow any
other error to surface real UI regressions.
- Around line 31-41: Escape the env-driven IDP value before using it in the
locator regex, since `setup.ts` builds `new RegExp(idpName, 'i')` directly in
the IDP selection flow. Update the `idpName` handling near the `idpScreenText`
check and `page.getByRole('link', { name: ... })` so special regex characters in
`process.env.IDP` are treated as literal text, preventing match failures or
regex errors during login setup.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@test/ui-e2e/global.setup.ts`:
- Around line 15-18: The catch block in global.setup.ts is masking real failures
from the cleanup command and incorrectly logging success. Update the error
handling around the execSync cleanup path so the catch in the setup flow does
not discard the thrown error; instead, surface the underlying failure details
and let the test setup fail or abort appropriately. Use the existing setup logic
around the execSync call and the log messages “Cluster sanitized” / “Cluster is
clean” to locate the block and replace the silent success path with explicit
error reporting.